perm filename ALAN.TO[1,JRA]1 blob
sn#480011 filedate 1979-10-05 generic text, type C, neo UTF8
COMMENT ā VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002 Alan,
C00012 ENDMK
Cā;
Alan,
i am forming a program committee for a lisp conference to be held next
year at stanford. i hope you consider your work sufficiently linked to
lisp in spirit that you would agree to serve on the committee.
i am attaching some preliminary information about the proposed agenda
and schedule. please look it over and give me a call at (408) 353-3857
or send response to jra@su-ai
some of the info is old: in particular stanford WILL host it aug 24-27.
also the committee now includes Mccarthy, hewitt, fateman, prini, dan friedman
with offers out to several more.
--------------------------------------------
.select 2
.once center
The LISP Conference
.select 1
%2PURPOSE.%1 Many areas of contemporary computer science have their spiritual
roots in developments related to LISP. The impact of LISP on AI
is well known. The thrust of this conference is the emphasis of
the non-AI contributions of LISP. These areas span architecture,
a unique view of programming, and a perception of the importance of
theory. The call for papers will reflect this breadth.
%2PROGRAM COMMITTEE.%1 In keeping with the international character
of LISP-related activities, I have invited
participants from several countries. Considering the geographical
dispersion and the time constraints, it is of critical importance that
our program committee be formed at once, and begin work.
%2THE CALL FOR PAPERS.%1 The following selection of topics is meant only as a guide.
The major concern is to attract participants outside of the traditional AI
areas.
.begin indent 5,10
%2Architecture.%1 Several groups are actively pursuing
the design and implementation of LISP hardware. These projects
range from re-microcoded
commercially available hardware to specially designed LISP chips.
%2Languages and Theory.%1 There are several research areas related to
LISP-like languages,
though the ancestry may be spiritual rather than physical.
For example,
papers on applicative languages, object-oriented languages and
formal semantics of LISP-like languages should be
requested.
%2Programming and Environments.%1 One important facet of LISP as
a programming language
is its flexible programming behavior including the support systems
which surround the language. These aspects of LISP should be represented
at our conference.
%2Applications.%1 LISP is finding great appeal outside the traditional
Artificial Intelligence area. We should offer our conference as a forum for
these new applications.
%2Note.%1 These areas are not exhaustive. All suggestions for revision
will be considered.
.end
%2PANEL DISCUSSION.%1 There should be a panel discussion involving the
topic "What is LISP?". Even informal conversations will
elicit several divergent if not contradictory views of LISP;
a organized effort should prove even more illuminating.
%2DATE.%1 Currently, the dates of August 24-27 1980 (with a party
on the evening of August 24), is most attractive. The preceding
week Stanford will host an AI meeting. Our conference should attract
many of those participants.
%2LOCATION.%1 The possibilities I am pursuing are the campus of
Stanford University and that of the University of Santa Clara (about
ten miles from Stanford). Both facilities have conference facilities,
lodging, and food services. Of course, a commercial facility could also be
used, but a campus atmosphere is advantageous.
%2SPONSORSHIP.%1 As yet unsponsored. I have heard conflicting reports about
the benefits of sponsorship. I will continue to investigate; perhaps
sponsorship is a question to be decided by the Program Committee.
%2QUESTIONS.%1 Several questions have occurred in this initial phase.
I would like your opinions, please.
.begin indent 5,10
Should the conference be sponsored, or should we try to maintain
our own financial control. It is at least conceivable that we
run the budget with a small capital outlay with the major expenses
to be covered by advance registration. On the other hand, if it
is to be sponsored, what agencies would you suggest?
A major concern is how to estimate attendance. Could you please
estimate how many people you would expect to attend from your
area or country? Could you also estimate the total conference
attendance.
.end
%2FINAL NOTE.%1 Time is a %2major%1 concern. Please respond as soon
as posssble. If you do %2not%1 feel that you can contribute the needed
effort I would appreciate it if you could direct me to alternate
candidates.
.group skip 6
Thank you for your time and consideration.
.group skip 4
John Allen
--------------------------------------------
oct 5
Tentative deadlines:
October 30: Call for papers announced through Net and underground (in
various countries), with an official notification ASAP. Letter to ACM
requesting ACM cooperation and listing of the conference in CACM goes
out today (Oct 5, 1979). The larger Call-for-papers must wait for the
completion of the committee.
(twenty weeks)
March 14: Papers due;
I would favor
a draft paper (size specified in number of words, not pages).
blind refereeing, even though the authorship can often be deduced.
each committee member reads (approx. 3) papers, possibly farming them out
to conscientious colleagues; of course the membership is ultimately
responsible for the papers. The logistics of acceptance/rejection
are to be worked out by the committee (before March 14);
therefore each author submits no. copies = size of committee.
(ten weeks)
May 23: Accept/Reject;
Ten weeks for the review process is within reason. This could be shrunk
if we need some extra lead time on the call-for-papers.
(seven weeks)
July 11: Final papers due;
Seven weeks for revision is generous.
(six weeks)
August 24: Conference begins;
This leaves six weeks for printing and binding. I have located
a printer (with an excellent reputation) who will promise a
three-week turn around, printed and bound.